fix(scan): error states for home txs, tokens, and address lists#101
Conversation
Phase 1 of the fetcher error-state rollout. fetchLatestTransactions, fetchAccountHistory, fetchNativeTokens/fetchTokens, and fetchAccountTokens returned [] on a failed request, so an outage looked like an empty list. They now return null on failure so the hook flags an error. Added a shared FetchError component and wired it into the home transactions list, the tokens page, and the address tx-history and token-holdings tabs.
|
Warning Review limit reached
More reviews will be available in 10 minutes and 27 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
satyakwok
changed the title
1 participant
Surfaces fetch errors in the home transactions list, the tokens page, and the address tx-history and token-holdings tabs (follows #100).
What changed
fetchLatestTransactions, fetchAccountHistory, fetchNativeTokens/fetchTokens, and fetchAccountTokens returned an empty array when the request failed, so the hook never saw an error and an outage rendered as a genuinely empty list. They now return null on failure. Added a shared FetchError component (warn EmptyState + retry) and wired it into those lists.
Testing
typecheck and build pass. Verified live: /tokens renders the retry state instead of an empty list while the endpoint is failing.